Skip to main content

This is a new service – your feedback will help us to improve it.

Tandridge District Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

Land at Carlton Road South Godstone

reference
89/GOD W2
name
Land at Carlton Road South Godstone
tree-preservation-order

undefined

89/GOD
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-0.069245 51.199833,-0.069263 51.199840,-0.069236 51.199611,-0.069445 51.199614,-0.069348 51.198901,-0.069025 51.198979,-0.068717 51.199125,-0.068456 51.199318,-0.068257 51.199518,-0.068013 51.199711,-0.067795 51.199937,-0.067667 51.199954,-0.067066 51.199549,-0.067032 51.199504,-0.066943 51.199471,-0.066923 51.199502,-0.066769 51.199513,-0.066639 51.199540,-0.066603 51.199578,-0.066627 51.199625,-0.066567 51.199757,-0.066390 51.199856,-0.066426 51.199882,-0.066365 51.199933,-0.066339 51.200002,-0.066320 51.200027,-0.066317 51.200109,-0.066270 51.200140,-0.066173 51.200285,-0.066072 51.200322,-0.066070 51.200379,-0.065994 51.200434,-0.066010 51.200498,-0.065971 51.200555,-0.065823 51.200649,-0.065748 51.200730,-0.065688 51.200755,-0.065660 51.200783,-0.065670 51.200874,-0.065595 51.200898,-0.065975 51.201419,-0.066078 51.201275,-0.066274 51.201628,-0.066434 51.201719,-0.066686 51.201755,-0.067232 51.201720,-0.067796 51.201697,-0.067912 51.201750,-0.068176 51.201309,-0.068279 51.201019,-0.068313 51.200638,-0.068236 51.200306,-0.068115 51.200158,-0.068309 51.200066,-0.068953 51.199860,-0.069245 51.199833)))
point
POINT (-0.067398 51.200514)
notes
organisation
entry-date
1972-11-30
start-date
1972-11-30
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Tandridge District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL